I have attached my code. This code works perfectly in some files, but the filter doesn't work at all in other files. I'm not sure what is wrong with it?
Thanks!
josiah820 - Fri Jun 08 13:21:53 EDT 2012 |
|
Re: DXL Acting Strangely? SystemAdmin - Sat Jun 09 03:35:56 EDT 2012
If the filter does not work, are you sure that the problem is within the DXL code?
Did you try to create the filter manually and apply it to the module?
You can add a "halt" statement in your code after the line "applyFiltering(l)" and go to the filter's properties to see which filter has eventually been applied.
Perhaps it is a matter of the dates (format, ...), not of the modules?
|
|
Re: DXL Acting Strangely? josiah820 - Mon Jun 11 08:44:26 EDT 2012 SystemAdmin - Sat Jun 09 03:35:56 EDT 2012
If the filter does not work, are you sure that the problem is within the DXL code?
Did you try to create the filter manually and apply it to the module?
You can add a "halt" statement in your code after the line "applyFiltering(l)" and go to the filter's properties to see which filter has eventually been applied.
Perhaps it is a matter of the dates (format, ...), not of the modules?
It works when I try to apply the filter manually, and when I check the filtering dialog box after the filter SHOULD have been applied, the filter is shown in the box, but it almost looks as if the applyFiltering command isn't working, but it works perfectly in the other files. What I really don't understand, though, is that the problem cannot be with the format of the dates, because they are formatted exactly the same in all of the files. I'm using the "Last Modified On" attribute. They are all formatted like: "Tuesday, November 02, 2011". I'm not sure what's going on with this.
Thanks!
|
|
Re: DXL Acting Strangely? josiah820 - Mon Jun 11 09:23:29 EDT 2012 josiah820 - Mon Jun 11 08:44:26 EDT 2012
It works when I try to apply the filter manually, and when I check the filtering dialog box after the filter SHOULD have been applied, the filter is shown in the box, but it almost looks as if the applyFiltering command isn't working, but it works perfectly in the other files. What I really don't understand, though, is that the problem cannot be with the format of the dates, because they are formatted exactly the same in all of the files. I'm using the "Last Modified On" attribute. They are all formatted like: "Tuesday, November 02, 2011". I'm not sure what's going on with this.
Thanks!
Never mind, I figured it out. Thanks!
|
|
Re: DXL Acting Strangely? SystemAdmin - Mon Jun 11 09:29:41 EDT 2012 josiah820 - Mon Jun 11 08:44:26 EDT 2012
It works when I try to apply the filter manually, and when I check the filtering dialog box after the filter SHOULD have been applied, the filter is shown in the box, but it almost looks as if the applyFiltering command isn't working, but it works perfectly in the other files. What I really don't understand, though, is that the problem cannot be with the format of the dates, because they are formatted exactly the same in all of the files. I'm using the "Last Modified On" attribute. They are all formatted like: "Tuesday, November 02, 2011". I'm not sure what's going on with this.
Thanks!
I'm not sure about all the "…apply…Filtering"-stuff and how it interacts with the command "filtering on", which was sufficient in DOORS 8.x, but:
Can it be that in some modules your view "Last Modified" is defined with filtering on and in others with filtering off?
I now see that you first switch on filtering and then load your view "Last Modified". Since the view definitions may override your filtering settings, the command "filtering off" will not always be effective. Switch lines 62 and 64 in your code and see whether this makes a difference.
|
|
Re: DXL Acting Strangely? SystemAdmin - Mon Jun 11 09:44:25 EDT 2012 josiah820 - Mon Jun 11 09:23:29 EDT 2012
Never mind, I figured it out. Thanks!
So, what was the solution?
|
|
Re: DXL Acting Strangely? josiah820 - Mon Jun 11 09:49:10 EDT 2012 SystemAdmin - Mon Jun 11 09:44:25 EDT 2012
So, what was the solution?
In all honesty, I didn't do anything. I was using a fake "test" file to test my programs on. I copied all of the files in our database into another Project folder and put "TEST" at the end of the file names. When I switched over to test on the files in our actual DOORS database, it worked perfectly. Doesn't really make a whole lot of sense, but it works on the real files for some reason.
|
|